Mobility management method, apparatus, and system

ABSTRACT

Embodiments of the present disclosure disclose a mobility management method, apparatus, and system, and pertain to the field of wireless communications technologies. The method includes: determining, by a first mobility management entity based on information about a PDN connection established by user equipment in a 4G network, a network slice corresponding to the PDN connection, and then determining, with reference to a subscribed network slice of the user equipment, a network slice allowed for the user equipment.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/849,435, filed on Apr. 15, 2020, which is a continuation ofInternational Application No. PCT/CN2017/106397, filed on Oct. 16, 2017.All of the afore-mentioned patent applications are hereby incorporatedby reference in their entireties.

TECHNICAL FIELD

Embodiments of the present disclosure relate to the field of wirelesscommunications technologies, and in particular, to a mobility managementmethod, apparatus, and system.

BACKGROUND

With rapid development of wireless communications technologies, the 5thgeneration (5G) mobile communications technology emerges. At an earlystage of network deployment, coverage of a 5G network is insufficient.Therefore, when a location of user equipment (UE) changes, the UE may behanded over between a 5G network and a 4th generation (4G) network toensure that a user can enjoy an equivalent service.

A DCN (dedicated core network) is a dedicated core network that isdefined in 4G by the 3rd Generation Partnership Project (3GPP) and thatis used to serve a specific type of service. The DCN includes one ormore mobility management entities (MME) and one or more serving gateways(SGW)/PDN gateways (PGW)/policy and charging rules functions (PCRF).Another core-network network element such as a home subscriber server(HSS) is shared by all DCNs. Operators may deploy a DCN to isolate aspecific user (for example, a subscriber belonging to a specificenterprise or a separate administrative domain), or to tailor networkfunctions for a specific service attribute (for example, a low-latencyhigh-reliability type). In 4G a network selects a DCN for UE based on auser equipment usage type (UE Usage Type). After the UE accesses a DCN,an MME serving the DCN sends a DCN identifier (DCN ID) to the UE. The UEadds the DCN ID to an RRC message when accessing the DCN next time, anda base station can quickly find, based on the DCN ID, the MME of the DCNthat the UE needs to access:

A concept of network slicing is introduced in 5G, and network slicing isan upgraded version of the DCN. The 5G network slicing is essentiallydifferent from a 4G DCN in terms of architectures. In the 4G DCN, a DCNis a dedicated network, and there is no association between DCNs. In 5G,a plurality of network slices may share a group of access and mobilitymanagement functions (AMF), each network slice has a slice-specificsession management function SMF), user plane function (UPF), and policycontrol function (PCF), and unified data management (UDM) is sharedamong all slices.

After 5G is introduced, network interworking between 5G and 4G exists.However, in the prior art, mapping between a DCN and a network slice isnot considered for interworking between 4G and 5G. For example, whenuser equipment moves from a coverage area of a 4G base station to acoverage area of a 5G base station, the prior art provides nocorresponding solution for how to ensure that the user equipment canstill enjoy a subscribed service equivalent to an original subscribedservice. In addition, when the user moves in the 5G network, and when anAMF currently serving the UE cannot continue to provide a service forthe UE, the prior art provides no corresponding solution for how toensure that the user equipment can access a corresponding network sliceby using another AMF.

SUMMARY

Embodiments of the present disclosure provide a mobility managementmethod, apparatus, and system, to resolve a problem of how to access acorresponding network slice when a location of user equipment changes.

To achieve the foregoing objectives, the embodiments of the presentdisclosure provide the following technical solutions.

According to a first aspect, a mobility management method is provided,and the method includes: obtaining, by a first mobility managemententity, information about an established PDN connection and informationabout a subscribed network slice of user equipment UE; and obtaining, bythe first mobility management entity based on the information about theestablished PDN connection and the information about the subscribednetwork slice, information about a network slice allowed for the UE. Theinformation about the established PDN connection may be specifically anidentifier of a session management function entity corresponding to thePDN connection or an access point name APN corresponding to the PDNconnection. Based on the information about the established PDNconnection, the first mobility management entity can obtain informationabout a network slice corresponding to the established PDN connection;and further, based on the information about the subscribed network sliceof the UE, the first mobility management entity can determine PDNconnections that can be handed over, network slices to which the PDNconnections of the UE can be handed over in a 5G network, and theinformation about the allowed network slice. Therefore, it is ensuredthat when moving from a 4G coverage area in which the user equipmentenjoys a DCN service in a 4G network to a coverage area of a 5G basestation, the user equipment can be handed over to a proper networkslice, and can still enjoy a network service equivalent to that in theoriginal 4G network. In particular, the user equipment can be handedover to a network slice instance corresponding to the PDN connection inthe 4G network, so that service continuity can be ensured while the userequipment can enjoy a network service equivalent to that in the original4G network.

The obtaining, by the first mobility management entity based on theinformation about the established PDN connection and the informationabout the subscribed network slice, information about a network sliceallowed for the LTE can be specifically implemented in the followingseveral possible manners.

in a possible implementation, the first mobility management entityobtains, based on the information about the established PDN connection,information about a network slice corresponding to the established PDNconnection; and the first mobility management entity obtains, based onthe information about the network slice corresponding to the establishedPDN connection and the information about the subscribed network slice,the information about the network slice allowed for the UE. The obtainedinformation about the network slice allowed for the UE can bespecifically determined by the first mobility management entity itselfbased on the information about the network slice corresponding to theestablished PDN connection and the information about the subscribednetwork slice, or the first mobility management entity may request anetwork slice selection function entity to determine the obtainedinformation about the network slice allowed for the UR For example, thefirst mobility management entity sends a slice selection request to thenetwork slice selection function entity, where the slice selectionrequest includes the information about the network slice correspondingto the established PDN connection and the information about thesubscribed network slice; and the first mobility management entityreceives a slice selection response returned by the network sliceselection function entity, where the slice selection response includesthe information about the network slice allowed for the UE. That thefirst mobility management entity obtains, based on the information aboutthe established PDN connection, information about the network slicecorresponding to the established PDN connection may be specifically:obtaining, by the first mobility management entity, the informationabout the network slice corresponding to the established PDN connectionfrom a session management function entity corresponding to theestablished PDN connection.

When the information about the established PDN connection is an FQDN ofa PGW-C/SME and the FQDN includes information about a network slice, thefirst mobility management entity or the network slice selection functionentity may determine, based on the FQDN, the information about thenetwork slice corresponding to the PDN connection. When the informationabout the established PDN connection is an IP address of the PCW-C/SMF,the first mobility management entity or the network slice selectionfunction entity may reversely query a domain name system (DNS) based onthe IP address, to obtain the FQDN of the PGW-C/SMF, and further obtain,according to the foregoing method, the information about the networkslice corresponding to the PDN connection. When the information aboutthe established PDN connection is an APN, the first mobility managemententity or the network slice selection function entity determines, basedon a preconfigured mapping relationship between an APN and S-NSSAI, theinformation about the network slice corresponding to the PDN connection.

In a possible implementation, the first mobility management entity mayrequest the network slice selection function entity to determine theinformation about the network slice allowed for the UE. The obtaining,based on the information about the established PDN connection and theinformation about the subscribed network slice, information about anetwork slice allowed for the UE is specifically: sending, by the firstmobility management entity, a slice selection request to the networkslice selection function entity, where the slice selection requestincludes the information about the established PDN connection and theinformation about the subscribed network slice; and receiving, by thefirst mobility management entity, a slice selection response returned bythe network slice selection function entity, where the slice selectionresponse includes the information about the network slice allowed forthe UE.

In another possible implementation, before the obtaining, by a firstmobility management entity, information about an established PDNconnection of user equipment UE, the method further includes: receiving,by the first mobility management entity, a first request message from anetwork device, where the first request message carries the informationabout the established PDN connection, and the first mobility managemententity is determined by the network device based on information about atarget access region of the UE and one of the following parameters: anidentifier of a dedicated core network accessed by the UE or a globallyunique temporary identifier GUTI of the UE, where the GUTI includesinformation about a mobility management entity serving the UE. The firstrequest message may be a handover request in step 303 in the embodimentof FIG. 3 or in step 403 in the embodiment of FIG. 4 , and the networkdevice may be a mobility management entity MME providing an accessservice for the UE before a handover.

Because a location of the LE changes, a mobility management entitycurrently serving the UE may not hand over all PDN connections of the UEto proper network slices in the 5G network. For a PDN connection thatcannot be handed over in established PDN connections of the UE in the 4Gnetwork, the first mobility management entity sends a PDN connectionhandover reject message to a third mobility management entity, where thePDN connection handover reject message includes information about thePDN connection that cannot be handed over. The third mobility managemententity releases the PDN connection that cannot be handed over, and thethird mobility management entity may be an MME in the 4G network.

According to a second aspect, a mobility management method is provided,and the method includes: obtaining, by a network device, a globallyunique temporary identifier GUTI of user equipment UE, where the GUTIincludes information about a mobility management entity serving the UE;and obtaining, by the network device based on the information about themobility management entity serving the UE and information about a targetaccess region, a mobility management entity that is to perform amobility handover. Specifically, a mapping relationship may beconfigured in the network device, and the network device queries themapping relationship based on the information about the mobilitymanagement entity serving the UE and the information about the targetaccess region, to determine the mobility management entity that is toperform a mobility handover. Alternatively, the mapping relationship maybe stored on another device in the network, and the network device maysend a query request to the another device, to obtain the mobilitymanagement entity that is to perform a mobility handover. When alocation of the UE changes, the mobility management entity that is toperform a mobility handover can be quickly determined according to themethod provided in this embodiment.

In a possible implementation, the information about the mobilitymanagement entity serving the UE is information about an AMF, and theinformation about the AMF includes information about a region in whichan AMF serving the UE is located and information about a set to whichthe AMF serving the UE belongs; and the determining, by the networkdevice based on the information about the mobility management entityserving the UE and information about a target access region, a mobilitymanagement entity that is to perform a mobility handover isspecifically: determining, by the network device based on theinformation about the region in which the AMF serving the UE is located,the information about the set to which the AMF serving the UE belongs,and the information about the target access region, the mobilitymanagement entity that is to perform a mobility handover. According tothe method provided in this embodiment, during a handover of the UE froma 5G network to a 4G network or when the UE moves within the 5G network,the mobility management entity that is to perform a mobility handovercan be quickly determined.

In a possible implementation, the information about the mobilitymanagement entity serving the UE is an identifier of the MME, and theidentifier of the MME includes an identifier of an MME group to whichthe MME belongs and a code number of the MME; and the determining, bythe network device based on the information about the mobilitymanagement entity serving the UE and information about a target accessregion, a mobility management entity that is to perform a mobilityhandover is specifically: determining, by the network device based onthe identifier of the MME and the information about the target accessregion, the mobility management entity that is to perform a mobilityhandover. The determining, by the network device based on the identifierof the MME and the information about the target access region, themobility management entity that is to perform a mobility handover may beimplemented in two possible manners: In one implementation, the networkdevice queries, based on the identifier of the MME and the informationabout the target access region, the mapping relationship stored locallyor on another device, to determine the mobility management entity thatis to perform a mobility handover. In the other implementation, thenetwork device determines an initial AMF region identifier based on theidentifier of the MME group in the identifier of the MME; and obtains aninitial AMF set identifier based on the code number of the MME; ordetermines an initial AMF region identifier and an initial AMF setidentifier based on the identifier of the MME group in the identifier ofthe MME. When a region corresponding to the information about the targetaccess region is in a region indicated by the initial AMF regionidentifier, the network device selects, from an AMF set indicated by theinitial AMF set identifier, one AMF as the mobility management entitythat is to perform a mobility handover. When a region corresponding tothe information about the target access region is not in a regionindicated by the initial AMF region identifier, the network deviceobtains a corresponding target AMF set based on the initial AMF regionidentifier, the initial AMF set identifier, and the information aboutthe target access region, and selects one AMF from the target AMF set asthe mobility management entity that is to perform a mobility handover.According to the method provided in this embodiment, when the UE movesfrom the 4G network to the 5G network, the mobility management entitythat is to perform a mobility handover can be quickly determined.

The network device may be a base station, or may be a mobilitymanagement entity in the 4G network or 5G network.

According to a third aspect, a mobility management apparatus isprovided, and the mobility management apparatus has functions ofimplementing the method according to the first and/or the second aspect.The functions may be implemented by hardware, or may be implemented byhardware executing corresponding software. The hardware or softwareincludes one or more modules corresponding to the functions.

According to a fourth aspect, a mobility management apparatus isprovided, including: a processor and a memory. The memory is configuredto store a computer executable instruction, and when the mobilitymanagement apparatus runs, the processor executes the computerexecutable instruction stored in the memory, so that the mobilitymanagement apparatus performs the mobility management method accordingto either of the first aspect and the second aspect.

According to a fifth aspect, a computer readable storage medium isprovided, where the computer readable storage medium stores aninstruction, and when the instruction is run on a computer, the computermay perform the mobility management method according to any possibleimplementation of the first aspect.

According to a sixth aspect, a computer program product including aninstruction is provided, where when the computer program product is runon a computer, the computer may perform the mobility management methodaccording to either of the first aspect and the second aspect.

According to a seventh aspect, a chip system is provided, and the chipsystem includes a processor, configured to support a mobility managementapparatus in implementing the functions in the foregoing aspects. In apossible design, the chip system further includes a memory, and thememory is configured to store a program instruction and data that arenecessary for the mobility management apparatus. The chip system mayinclude a chip, or may include a chip and another discrete device.

For technical effects brought by any design manner in the third aspectto the seventh aspect, refer to the technical effects brought bydifferent design manners in the first aspect and second aspect. Detailsare not described herein again.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of an architecture of a mobilitymanagement system according to an embodiment of this application;

FIG. 2 is a schematic diagram of a hardware structure of a mobilitymanagement apparatus according to an embodiment of this application;

FIG. 3 is a schematic flowchart of a mobility management methodaccording to an embodiment of this application;

FIG. 4 is a schematic flowchart of another mobility management methodaccording to an embodiment of this application;

FIG. 5 is a schematic flowchart of still another mobility managementmethod according to an embodiment of this application;

FIG. 6 is a schematic flowchart of yet another mobility managementmethod according to an embodiment of this application;

FIG. 7 is a schematic flog of still yet another mobility managementmethod according to an embodiment of this application;

FIG. 8 is a schematic flowchart of a further mobility management methodaccording to an embodiment of this application;

FIG. 9 is a schematic flowchart of a still further mobility managementmethod according to an embodiment of this application;

FIG. 10 is a schematic flowchart of a yet further mobility managementmethod according to an embodiment of this application;

FIG. 11 is a schematic structural diagram of a mobility managementapparatus according to an embodiment of this application; and

FIG. 12 is a schematic diagram of a mobility management system accordingto an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

To make the objectives, technical solutions, and advantages of thepresent disclosure clearer, the following further describes theembodiments of the present disclosure with reference to the accompanyingdrawings. Apparently, the described embodiments are merely some ratherthan all of the embodiments of the present disclosure. A specificoperation method in a method embodiment may also be applied to anapparatus embodiment or a system embodiment.

A network architecture and a service scenario are described in theembodiments of the present disclosure to describe the technicalsolutions in the embodiments of the present disclosure more clearly, butdo not constitute a limitation on the technical solutions provided inthe embodiments of the present disclosure. A person of ordinary skill inthe art may understand that, as the network architecture evolves and anew service scenario emerges, the technical solutions provided in theembodiments of the present disclosure are also applicable to a similartechnical problem.

A mobility management method provided in the embodiments of the presentdisclosure can be applied in a system 100 shown in FIG. 1 . In thesystem 100, an evolved universal terrestrial radio access network(E-UTRAN) includes at least a 4G base station (for example, an e-NodeB),and a next-generation radio access network (NG-RAN) includes at least a5G base station. User equipment UE in this application may includevarious handheld devices, in-vehicle devices, wearable devices, andcomputing devices that have a wireless communication function, or otherprocessing devices connected to a wireless modem, and user equipment(UE), terminals, terminal equipment, software terminals, and the likethat are in various forms. For ease of description, in this application,the devices mentioned above are collectively referred to as userequipment or UE. In an architecture of interworking between 4G and 5Gshown in FIG. 1 , a 4G network and a 5G network share UPF+PGW-U,SMF+PGW-C, PCF+PCRF, or UDM+HSS. “+” herein represents co-location of arelated network function entity in 5G and a network element in 4G. Forexample, the UPF is a user plane function in 5G, the PGW-U is a gatewayuser plane function in 4G corresponding to the UPF, and UPF+PGW-U isbriefly referred to as a user plane function entity in the embodimentsof the present disclosure; the SMF is a session management function in5G, the PGW-C is a gateway control plane function in 4G corresponding tothe SMF, and the SMF+PGW-C is briefly referred to as a sessionmanagement function entity; the PCF is a policy control function in 5G,the PCRF is a corresponding policy and charging rules function in 4G,and the PCF+PCRF is briefly referred to as a policy control functionentity the UDM is unified data management in 5G, the HSS is a homesubscriber server in 4G, and the HSS+UDM is briefly referred to as auser data management entity. In the interworking architecture, an MMEand an AMF interwork with each other through an N26 interface, and theinterface is used for transfer of a context of the UE and a handoverprocess. In addition, the base station in the 4G network is connectedthrough an SGW to the PGW-C/U. For related interfaces in the figure,refer to the prior art. Details are not described in the embodiments ofthe present disclosure.

In addition, a network slice selection function (NSSF) entity in FIG. 1is configured to select a network slice. When the AMF cannot select anetwork slice for the UE, the AMF requests the NSSF to select a networkslice for the UE.

When the UE moves from an E-UTRAN coverage area to an NG-RAN coveragearea, or from an NG-RAN coverage area to an E-UTRAN coverage area, orwhen the AMF currently serving the UE cannot continue to provide aservice for the UE because the UE moves, the mobility management methodprovided in the embodiments of the present disclosure is triggered.

During a handover of the user equipment from the 4G network to the 5Gnetwork, to ensure service continuity of the user equipment, a PDNconnection of the user equipment in the 4G network needs to be mapped toa PDU session in a corresponding network slice instance in 5G. Becausethe MME possibly fails to select a network slice, when the userequipment needs to be handed over from a PDN connection in the 4Gnetwork to a PDU session in a 5G core network, the MME possibly fails toselect a proper AMF for the user equipment. In a possibleimplementation, the MME selects a default AMF. After receiving ahandover request sent by the MME, the default AMF may request the NSSFto allocate a target AMF to the user equipment. In another possibleimplementation, a mapping relationship between a DCN identifier and anAMF set is configured in the MME, and the MME determines a target AMFbased on a DCN identifier corresponding to the user equipment. It isconsidered that after the user equipment is handed over to 5G, a new PDUsession is further created subsequently. Therefore, a 5G core networkfurther needs to determine information about a network slice allowed forthe user equipment (Allowed NSSAI).

Specifically, the 5G core network first determines, based on informationabout an established PDN connection of the user equipment in the 4Gnetwork, a network slice corresponding to the PDN connection, and thendetermines, with reference to a subscribed network slice of the userequipment and a location of the user equipment, PDN connections that canbe handed over to the 5G core network and network slices allowed for theuser equipment.

In addition, during a handover of the user equipment from the 5G networkto the 4G network, the 5G core network (AMF) obtains a user equipmentusage type (UE usage type) from the user data management entity, andselects a target MME based on the UE usage type. Because not all PDUsessions can be handed over to the 4G network, some PDU sessions mayneed to be discarded in the handover process.

As shown in FIG. 2 , a node shown in FIG. 1 , such as the MME, the AMF,the E-UTRAN, or the NG-RAN may be implemented in a form of a computerdevice (or system) in FIG. 2 .

FIG. 2 is a schematic diagram of a computer device 200 according to anembodiment of the present disclosure. The computer device 200 includesat least one processor 21, a communications bus 22, a memory 23, and atleast one communications interface 24.

The processor 21 may be a general-purpose central processing unit (CPU),a microprocessor, an application-specific integrated circuit (ASIC), orone or more integrated circuits configured to control program executionof the solutions of the present disclosure.

The communications bus 22 may include a path, through which informationis transferred between the foregoing components. The communicationsinterface 24 uses any apparatus such as a transceiver to communicatewith another device or another communications network, such as anEthernet, a radio access network (RAN), or a wireless local area network(WLAN).

The memory 23 may be but is not limited to: a read-only memory oranother type of static storage device capable of storing staticinformation and instructions, a random access memory (RAM) or anothertype of dynamic storage device capable of storing information andinstructions, an electrically erasable programmable read-only memory(EEPROM), a compact disc read-only memory (CD-ROM) or another compactdisc storage, an optical disc storage (including a compact disc, a laserdisc, an optical disc, a digital versatile disc, a Blu-ray disc, or thelike), a magnetic disk storage medium or another magnetic storagedevice, or any other medium that can be used to carry or store expectedprogram code in an instruction or data structure form and that can beaccessed by a computer. The memory may exist independently, and isconnected to the processor by using a bus. Alternatively, the memory maybe integrated with the processor.

The memory 23 is configured to store application program code used toexecute the solutions of the present disclosure, and the execution iscontrolled by the processor 21. The processor 21 is configured toexecute the application program code stored in the memory 23.

During specific implementation, in an embodiment, the processor 21 mayinclude one or more CPUs, for example, a CPU 0 and a CPU 1 in FIG. 2 .

During specific implementation, in an embodiment, the computer device200 may include a plurality of processors, for example, the processor 21and a processor 28 in FIG. 2 . Each of these processors may be asingle-core (single-CPU) processor, or may be a multi-core (multi-CPU)processor. The processor herein may be one or more devices, circuits,and/or processing cores configured to process data (for example, acomputer program instruction).

During specific implementation, in an embodiment, the computer device200 may further include an output device 25 and an input device 26. Theoutput device 25 communicates with the processor 21, and may displayinformation in a plurality of manners. For example, the output device 25may be a liquid crystal display (LCD), a light emitting diode (LED)display device, a cathode ray tube (CRT) display device, a projector, orthe like. The input device 26 communicates with the processor 21, andmay receive an input of a user in a plurality of manners. For example,the input device 26 may be a mouse, a keyboard, a touchscreen device, asensor device, or the like.

The foregoing computer device 200 may be a general-purpose computerdevice or a dedicated computer device. During specific implementation,the computer device 200 may be a desktop computer, a portable computer,a network server, a personal digital assistant (PDA), a mobile phone, atablet computer, a wireless terminal device, a communications device, abuilt-in device, or a device having a structure similar to that in FIG.2 . The embodiments of the present disclosure impose no limitation on atype of the computer device 200.

For example, a node in FIG. 1 , such as the MME, the AMF, the E-UTRAN,or the NG-RAN may be a device shown in FIG. 2 . One or more softwaremodules are stored in a memory of the MME. The software module may beimplemented for the MME by using the processor and the program code inthe memory, to implement the mobility management method.

The following describes the mobility management method provided in thisembodiment of the present disclosure with reference to the flowcharts.

FIG. 3 is a schematic flowchart of a mobility management method. In thisembodiment, UE currently has accessed a 4G network by using a sourcebase station (a base station in the 4G network, for example, anE-UTRAN), and the UE is in a connected state. When the source basestation finds that the UE needs to be handed over, the source basestation selects a target base station. In this embodiment, the targetbase station selected by the source base station is a base stationconnected to a 5G core network (for example, an NG-RAN). The source basestation sends a handover request to an MME that provides a DCN servicefor the user equipment in the 4G network, to initiate a handoverprocedure.

Step 301: The source base station sends a first request message to theMME, where the first request message includes information about a targetaccess region. The MME receives the first request message.

Specifically, the first request message may be a handover request, andthe first request message may be sent by the source base station to theMME after a decision is made based on cell measurement informationreported by the user equipment. Optionally, the first request messagefurther includes information that can be used to determine the userequipment, for example, an identifier of the UE. The information aboutthe target access region may include at least one of an identifier of atarget cell, an identifier of the target base station, and an identifierof a target tracking area. The identifier of the target cell is used touniquely identify a target cell, and the target cell is a cell to beaccessed by the UE. The identifier of the target base station is used touniquely identify a target base station, and the target base station isa base station to which the to-be-accessed cell belongs. The identifierof the target tracking area is used to uniquely identify a targettracking area, and the target tracking area is a tracking area in whichthe to-be-accessed cell is located.

Step 302: The MME determines an initial AMF.

Specifically, the MME may determine, based on the information about thetarget access region, whether the handover request is for a handoverbetween different networks. For example, when the information about thetarget access region includes the identifier of the target base station,the MME may determine a type of the target base station based on theidentifier of the target base station, and determine, based on the type,whether the first request message is for a handover between differentnetworks. In a scenario in this embodiment of the present disclosure,the target base station is a base station in a 5G network. Therefore,the MME determines that the first request message is for an inter-systemhandover. To implement the inter-system handover, the MME needs todetermine, based on the information about the target access regioncarried in the first request message, an AMF that is to perform ahandover operation.

In a possible implementation, a mapping relationship between the MME andan AMF set is configured in the MME. The mapping relationship betweenthe MME, and the AMF set records a correspondence between a DCN ID, atarget region, and a corresponding AMF set, or a correspondence betweenan identifier of the MME, the target region, and the corresponding AMFset, as shown in the following table.

TABLE 1 DCN-ID or identifier Target AMF of the MME region set A Y B A XC

The identifier of the MME includes an MME group identifier (MMEGI) andan MME code number (MME Code). After receiving the first request messagesent by the source base station, the MME obtains a context of the UEbased on the identifier of the UE carried in the first request message.The context includes an identifier of a dedicated core network accessedby the UE, or an identifier of a mobility management entity serving theUE. The MME determines a corresponding target region based on theinformation about the target access region, further determines acorresponding AMF set with reference to the mapping relationship and theidentifier of the dedicated core network accessed by the UE or theidentifier of the mobility management entity serving the UE, andselects, according to a corresponding policy, one AMF from thedetermined AMF set as the initial AMF. The policy may be specifically amethod for determining one AMF from the AMF set based on informationsuch as priorities, capacities, load, or the like of AMFs in the UE set.

In another possible implementation, the MME group identifier (MMEGI) andthe MME code number (MME Code) are carried in a globally uniquetemporary identifier (GUTI) of the UE. When receiving the first requestmessage sent by the source base station, the MME obtains a context ofthe UE, where the context includes the GUTI of the UE, and the MME candirectly determine an AMF set based on the GUTI of the UE and a mappingrule. According to the mapping rule, the MMEGI in the GUTI of the UE isspecifically mapped to an AMF region identifier (AMF Region ID), and theMME code number (MME Code) is mapped to an AMF set identifier (AMF SetID). The MME determines a target AMF set and an AMF based on the mappedAMF region ID and AMF set ID and the information about the target accessregion. If the information about the target access region is in an AMFregion corresponding to the mapped AMF region ID, an AMF in an AMF setcorresponding to the mapped AMF region ID and AMF set ID is selected asthe initial AMF; otherwise, the target AMF set and the AMF are selectedbased on the mapped AMF region ID and AMF set ID and the informationabout the target access region. To support the foregoing selection, thefollowing table is configured for a system:

TABLE 2 Source AMF Source AMF Target Target AMF region set region set XA Y B . . . . . . . . . . . .

For example, the MME determines, according to the mapping rule, that theAMF region is X, the AMF set is A, and a target region Y correspondingto the information about the target access region is not in X. The MMEdetermines, according to the foregoing configuration table for thesystem, that a proper AMF set is B, and selects one AMF from B as theinitial AMF according to a preset policy.

According to the method for determining an initial AMF, the MME candetermine the initial AMF by the MME itself, or may determine theinitial AMF by querying another device in a network, for example, adomain name system (DNS). When the MME determines the initial AMF byquerying the DNS, the foregoing Table 1 and Table 2 are configured inthe DNS. The MME sends related information to the DNS and the DNSreturns a selected initial AMF to the MME.

Step 303: The MME sends a second request message to the determinedinitial AMF (namely, an AMF 1 in FIG. 3 ), where the second requestmessage carries information about an established PDN connection. The AMF1 receives the second request message sent by the MME.

Specifically, the second request message may be a handover request. Theinformation about the established PDN connection includes informationabout a PGW-C/SMF corresponding to the PDN connection, for example, mayinclude an Internet Protocol address (IP address) or a fully qualifieddomain name (FQDN) of the PGW-C/SMF. Optionally, the information aboutthe PDN connection may alternatively be an access point name (APN)corresponding to the PDN connection.

Step 304: After receiving the second request message sent by the MME,the AMF 1 obtains, based on the information about the established PDNconnection carried in the second request message, information about anetwork slice corresponding to the established PDN connection.

It should be noted that, the user equipment may previously establish aplurality of PDN connections in the 4G network. Therefore, theinformation about the established PDN connection herein may indicate aplurality of PDN connections, and information about a network slicecorresponding to each PDN connection can be determined in this step.

Specifically, in a possible implementation, when the information aboutthe established PDN connection is the FQDN of the PGW-C/SW, and the FQDNincludes information about a network slice, the information about thenetwork slice corresponding to the PDN connection, such as singlenetwork slice selection assistance information (S-NSSAI) and anidentifier of a network slice instance (NSI), can be determined based onthe FQDN. When the information about the established PDN connection isthe IP address of the PGW-C/SMF, the AMF 1 can reversely query thedomain name system (DNS) based on the IP address, to obtain the FQDN ofthe PGW-C/SMF, and further obtain, according to the foregoing method,the information about the network slice corresponding to the PDNconnection.

In another possible implementation, when the information about theestablished PDN connection is the APN, a mapping relationship between anAPN and S-NSSAI needs to be preconfigured in the AMF 1. When receivingthe second handover request, the AMF 1 determines, based on the mappingrelationship and the APN carried in the second handover request, S-NSSAIcorresponding to the PDN connection. It should be noted that there is aconstraint on this implementation. To be specific, the AMF 1 canaccurately determine, based on the APN only when the S-NSSAIcorresponding to the PDN connection corresponds to only one networkslice instance, a network slice instance corresponding to the PDNconnection, to ensure service continuity when the UE is handed over froma PDN connection in the 4G network to a PDU session in the 5G networksubsequently. When the S-NSSAI corresponding to the PDN connectioncorresponds to a plurality of network slice instances, during a handoverof the UE from a connection in the 4G network to a PDU session in the 5Gnetwork according to the method, a similar network service may beprovided for the UE but a short-time service interruption may occurbecause the UE may access another network slice instance thatcorresponds to the S-NSSAI corresponding to the PDN connection.

In another possible implementation, when the information about theestablished PDN connection is an identifier (the FQDN or the IP address)of the PGW-C/SMF, the AMF 1 sends, to the PGW-C/SMF based on theidentifier of the PGW-C/SMF, a request for obtaining the network slicecorresponding to the PDN connection. The PGW-C/SMF determinesinformation about a network slice to which the PGW-C/SMF belongs, andreturns a response message to the AMF 1, where the response messagecarries the information about the network slice corresponding to the PDNconnection.

Step 305: The AMF 1 obtains subscription data of the UE from a user datamanagement entity (HSS/UDM).

Specifically, because subscription data related to a network slice in 5Gis different from that in 4G, a subscribed network slice of the UE in 5Gcannot be mapped directly by the UE usage type. Therefore, the AMF 1needs to obtain information about the subscribed network slice of the UEfrom the user data management entity, including subscribed S-NSSAI.Optionally, the information about the subscribed network slice furtherincludes information such as a DNN corresponding to the subscribedS-NSSAI.

It should be noted that, step 304 and step 305 may be interchanged, ormay be performed simultaneously. This embodiment of the presentdisclosure imposes no limitation on the order of 304 and 305.

Step 306: The AMF 1 sends a slice selection request to a network sliceselection function (NSSF). The NSSF receives the slice selection requestsent by the AMF 1.

It should be noted that a solution in which the AMF 1 determines, basedon the information about the PDN connection, the network slicecorresponding to the PDN connection is provided in step 304 in thisembodiment of the present disclosure. In practice, the determining,based on the information about the PDN connection, the network slicecorresponding to the PDN connection can also be implemented by the NSSF.

Specifically, when the AMF 1 can determine, based on the informationabout the PDN connection, the network slice corresponding to the PDNconnection, that is, after step 304 is performed, the slice selectionrequest includes the information about the network slice correspondingto the established PDN connection (for example, corresponding S-NSSAI,and an identifier of an optional network slice instance), theinformation (for example, subscribed S-NSSAI) about the subscribednetwork slice of the UE, and the like.

When the AMF 1 cannot determine, based on the information about the PDNconnection, the network slice corresponding to the PDN connection, thatis, step 304 is not performed in this embodiment of the presentdisclosure, the AMF 1 needs to send the information about theestablished PDN connection to the NSSF. Specifically, the sliceselection request includes the information about the established PDNconnection, the information about the subscribed network slice of theUE, and the like. The method for determining, by the NSSF based on theinformation about the PDN connection, the network slice corresponding tothe PDN connection is the same as the method for determining, by the AMF1, the network slice corresponding to the PDN connection. Details arenot described herein again.

Step 307: The NSSF returns a slice selection response to the AMF 1,where the slice selection response includes information about a networkslice allowed for the UE (Allowed NSSAI) and information about a targetAMF set. The AMF 1 receives the slice selection response sent by theNSSF.

Specifically, the NSSF determines, based on the information about thenetwork slice corresponding to the established PDN connection, theinformation about the subscribed network slice of the UE, and the like,the target AMF set providing access for the UE and the allowed NSSAI.The NSSF sends the target AMF set and the information about the networkslice allowed for the UE allowed NSSAI to the initial AMF.

Optionally, the NSSF may get intersection of the network slicecorresponding to the established PDN connection of the UE and thesubscribed network slice of the UE, to determine the network sliceallowed for the UE and the corresponding target AMF set; or get a unionof the subscribed network slice of the UE and the network slicecorresponding to the established PDN connection of the UE, to determinethe network slice allowed for the UE and the corresponding target AMFset. This embodiment of the present disclosure imposes no limitation onthe method for determining, by the NSSF based on the network slicecorresponding to the established PDN connection (including the S-NSSAIand the identifier of the NSI) and the information about the subscribednetwork slice of the UE, the network slice allowed for the UE.

The AMF 1 receives the slice selection response returned by the NSSF.When the AMF 1 determines, based on the target AMF set, that the AMF 1can provide a service for the selected network slice, a subsequenthandover procedure (namely, step 314) is directly performed. When theAMF 1 determines, based on the target AMF set, that the AMF 1 cannotprovide a service for the selected network slice, the following steps308 to 310 may be performed, that is, the MME selects one target AMFfrom the target AMF set for the UE; or steps 311 and 312 may beperformed, that is, the AMF 1 selects one target AMF from the target AMFset for the UE, and sends a handover request to the target AMF.

It should be noted that, when the initial AMF determined in step 302 isaccurate, the initial AMF can always provide a service for the UE. Inthis case, the initial AMF is an ultimate AMF that provides an accessservice for the UE. In this case, steps 306 and 307 can be replaced bythat the AMF 1 itself determines the information about the network sliceallowed for the UE. To be specific, the AMF 1 determines, based on theinformation about the network slice corresponding to the established PDNconnection of the UE and the information about the subscribed networkslice of the UE, the information about the network slice allowed for theUE. The method for determining, by the AMF 1, the information about thenetwork slice allowed for the UE is the same as that used by the NSSF.

Step 308: The AMF 1 sends a handover reject message to the MME, and theMME receives the handover reject message sent by the AMF 1.

The handover reject message includes the information about the networkslice allowed for the UE and the target AMF set.

Step 309: The MME receives the handover reject message sent by the AMF1, and the MME selects one AMF from the target AMF set as a target AMF.

This embodiment of the present disclosure imposes no limitation on aspecific method for selecting, by the MME, one AMF from the target AMFset as a target AMF.

Step 310: The MME sends a third request message to the selected targetAMF (an AMF 2 in FIG. 3 ), where the third request message includes theinformation about the network slice allowed for the UE. The AMF 2receives the third request message sent by the

The third request message may be a handover request.

Step 311: The AMF 1 selects one AMF from the target AMF set as a targetAMF

Step 312: The AMF 1 sends the third request message to the selectedtarget AMF (the AMF 2 in FIG. 3 ), where the third request messageincludes the information about the network slice allowed for the UE. TheAMF 2 receives the third request message sent by the MME.

The third request message may be a handover request.

It should be noted that, the AMF 1 or the AMF 2 may determine, based onthe information about the established PDN connection and the informationabout the network slice allowed for the UE, a PDN connection that cannotbe handed over. For the PDN connection that cannot be handed over, theAMF 1 or the AMF 2 may return the handover reject message to the MME,where the handover reject message includes information about the PDNconnection that cannot be handed over. Specifically, the AMF 1 or theAMF 2 may determine, based on the network slice allowed for the UE andthe network slice corresponding to the established PDN connection,whether the network slice corresponding to the established PDNconnection is included in the network slice allowed for the UE. If thenetwork slice corresponding to the established PDN connection is notincluded in the network slice allowed for the UE, the AMF 1 or the AMF 2determines that the PDN connection cannot be handed over. Afterdetermining the PDN connection that cannot be handed over, the AMF 1 orthe AMY 2 returns the handover reject message to the MME, where thehandover reject message carries the information about the PDN connectionthat cannot be handed over, so that the subsequently initiates acorresponding PDN connection release procedure.

In this embodiment of the present disclosure, during a handover of theUE from the 4G network to the 5G network, the MME determines the initialAMF. Then the initial AMF obtains, based on the information about theestablished PDN connection of the UE in the 4G network, the networkslice corresponding to the established PDN connection of the UE, andfurther obtains, with reference to the information about the subscribednetwork slice of the UE, and the like, a network slice corresponding tothe PDN connection that can be handed over to the 5G network. Therefore,it is ensured that when moving from a 4G coverage area in which the userequipment enjoys a DCN service in the 4G network to a coverage area of a5G base station, the user equipment can be handed over to a propernetwork slice, and can still enjoy a network service equivalent to thatin the original 4G network. The user equipment can be handed over to anetwork slice instance corresponding to the PDN connection in the 4Gnetwork, so that service continuity can be ensured while the userequipment can enjoy a network service equivalent to that in the original4G network.

In step 307 in the foregoing embodiment, it is mentioned that theinitial AMF may be included in the target AMF set. When a networkarchitecture is relatively simple, or the mapping relationship,configured in the MME, from the MME to the AMF set is accurate enough,it can be ensured, to an extent, that the selected initial AMF isincluded in the target AMF set. In this case, the AMF first determinesPDN connections that can be handed over to the 5G network, and thenhands over the PDN connections to a corresponding network slice in the5G core network. Subsequently the 5G core network determines, based oninformation such as the subscribed network slice of the user equipment,the network slice allowed for the user equipment. For the PDNconnections that correspond to a network slice that is not included inthe network slice allowed for the user equipment, the 5G core networkreleases corresponding PDU sessions. In this way, a delay caused duringa handover of the user equipment from the 4G network to the 5G networkis reduced. As shown in FIG. 4 , an embodiment of the present disclosureprovides another mobility handover method.

Step 401: A source base station (E-UTRAN) sends a first handover requestto an MME, where the first handover request includes information about atarget access region. The MME receives the first handover request sentby the source base station.

Step 402: The MME determines an AMF.

Step 403: The MME sends a second handover request to the determined AMF,where the second handover request carries information about anestablished PDN connection. The AMF receives the second handover requestsent by the MME.

The information about the established PDN connection includes anidentifier of a PGW-C/SMF corresponding to the PDN connection.

Steps 401 to 403 are the same as steps 301 to 303. For related content,refer to the foregoing descriptions. Details are not described hereinagain.

Step 404: The AMF determines, based on the information about theestablished PDN connection, a PDN connection that can be handed over.

Specifically, for a PDN connection, the AMF determines, based on theinformation about the established PDN connection, whether the AMF cancommunicate with the corresponding PGW-C/SMF. If the AMF can communicatewith the corresponding PGW-C/SMF, the AMF determines that the PDNconnection can be handed over to the 5G network; otherwise, the PDNconnection cannot be handed over to the 5G network.

Optionally, the AMF sends a handover reject message to the MME, wherethe handover reject message includes information about a PDN connectionthat cannot be handed over, and the information about the PDN connectionthat cannot be handed over is used to notify the MME of PDN connectionsthat cannot be handed over to the 5G network. After receiving themessage, the MME initiates release of the PDN connection. The messagemay be carried in a response message for the handover request, and sentto the MME.

Step 405: Perform a subsequent handover procedure in which a PDNconnection in a 4G network that can be handed over to a 5G network ishanded over to a corresponding network slice in the 5G network.

Step 406: After the handover procedure ends, UE initiates a registrationrequest to the AMT.

Optionally, the registration request may include requested NSSAI of theUE.

Step 407: The AMF obtains subscription data of the UE from a user datamanagement entity.

Step 408: The AMF obtains information about a network slice allowed forthe UE.

The AMF may request an NSSF to determine, for the UE, the informationabout the allowed network slice, or the AMF itself may determine, forthe UE, the information about the allowed network slice. For relatedcontent, refer to the descriptions in steps 306 and 307 in the foregoingembodiment. Details are not described herein again.

Step 409: The AMF determines a PDU session that needs to be released,and sends a session release request to a session management functionentity. The session management function entity receives the sessionrelease request sent by the AMF.

For the PDN connection that is handed over in step 405, if a networkslice corresponding to the PDN connection does not belong to the networkslice allowed for the UE, the AMF needs to initiate the PDU sessionrelease request, to request the session management function entity torelease the corresponding PDU session.

Step 410: The AMF returns a registration response to the UE, where theregistration response carries the information about the network sliceallowed for the UE.

It should be noted that step 410 and step 409 can be interchanged.

In this embodiment of the present disclosure, during a handover of theUE from the 4G network to the 5G network, the MME first determines theAMF. Then the AMF determines, based on the information about theestablished PDN connection of the UE in the 4G network, PDN connectionsthat can be handed over to the 5G network. For the PDN connections thatcan be handed over to the 5G network, a handover to a 5G core network isfirst implemented, thereby preferably ensuring service continuity for auser, and reducing a handover delay. After the handover is implemented,it is then determined whether network slices corresponding tohanded-over PDN connections are network slices allowed for the UE. For aPDN connection that correspond to a network slice that is not includedin the network slices allowed for the UE, the 5G core network initiatesthe PDU session release request, to release a related PDU session,thereby ensuring rights and interests of an operator.

When UE is in a connected state, in some specific scenarios, there isinterface communication between an MME and an NSSF in a network. Asshown in FIG. 5 , an embodiment of the present disclosure providesanother mobility handover method.

Step 501: A source base station sends a handover request to the MME,where the handover request includes information about a target accessregion.

Step 502: The MME obtains information about an established PDNconnection of user equipment from a context of the UE, and determines acorresponding network slice based on the information about theestablished PDN connection.

Step 503: The MME obtains subscription data of the UE from a user datamanagement entity (HSS/UDM).

Step 504: The MME sends a slice selection request to the network sliceselection function (NSSF), The NSSF receives the slice selection requestsent by the MME.

Step 505: The NSSF returns a slice selection response to the MME, wherethe slice selection response includes information about a network sliceallowed for the UE (Allowed NSSAI) and information about a target AMFset.

Step 506: The MME selects one AMF from the target AMF set as a targetAMF.

Step 507: The MME sends a second handover request to the AMF, where thesecond handover request includes the information about the network sliceallowed for the UE.

In the foregoing steps, step 501 is the same as step 301 in theforegoing embodiment, step 502 is the same as step 304 in the foregoingembodiment, step 503 is the same as step 305, step 504 is the same asstep 306, step 505 is the same as step 307, and step 506 is the same asstep 311. For related content, refer to the related descriptions.Details are not described herein again.

FIG. 6 is a schematic flowchart of a mobility management method. In thisembodiment, UE first registers with an MME in a 4G network by using a 4Gbase station, and the MME sends a DCN identifier and a 4G GUTI to theUE. Then the UE enters an idle state for a reason, and moves into acoverage area of a 5G base station. The UE registers with a 5G corenetwork by using the 5G base station. In this embodiment, the UE movesto the coverage area of the 5G base station, and initiates aregistration request to the 5G base station, to initiate a handoverprocedure.

Step 601: The UE registers with the 4G network by using the MME.

When the LE accesses the 4G network, the network selects a DCN for theUE, and the MME allocates the 4G GUTI to the UE. The 4G GUTI includesinformation about the MME, for example, an MME group identifier (MMEGI)and an MME code number (MME CODE).

Step 602: The UE initiates a registration request to the 5G basestation, where the registration request includes a 5G GUTI mapped by theUE from the 4G GUTI. Optionally, the registration request furtherincludes information about a network slice requested by the UE(Requested NSSAI). Optionally, the registration request further includesan identifier of a DCN accessed by the UE in the 4G network. The 5G basestation receives the registration request sent by the UE.

That the UE maps the 4G GUTI to the 5G GUTI is specifically: mapping theMME group identifier to an AMF region identifier, and mapping the MMEcode number to an AMF set identifier; or mapping a part of the MME groupidentifier to an AMF region identifier, and mapping the other part ofthe MME group identifier to an AMF set identifier, for example, mappingeight high bits of the MME group identifier to the AMF regionidentifier, and mapping eight low bits of the MME group identifier tothe AMF set identifier.

Step 603: The 5G base station determines an initial AMF (an AMF 1 inFIG. 6 ), and forwards the registration request to the AMF 1.

The 5G base station determines an initial AMF in a plurality of methods.

In a possible implementation, the base station determines the initialAMF based on the information, carried in the registration request, aboutthe network slice requested by the UE.

In another possible implementation, a default AMF is configured in thebase station. When receiving the registration request, the base stationuses the default AMF as the initial AMF.

For still another possible implementation, refer to step 302 in theembodiment of FIG. 3 . The base station determines a region in which thebase station is located, determines the initial AMF set according toTable 1 with reference to the region in which the base station islocated, and the DCN ID or an identifier of the MME, and selects one AMFfrom the initial AMF set as the initial AMF.

For yet another possible implementation, refer to step 302 in theembodiment of FIG. 3 . The base station determines whether a region inwhich the base station is located is the same as an AMF region indicatedby the 5G GUTI. If the region in which the base station is located isthe same as the AMF region indicated by the 5G GUTI, the base stationselects one AMF, as the initial AMF, from an AMF set indicated by the 5GGUTI; if the region in which the base station is located is differentfrom the AMF region indicated by the 5G GUTI, the base stationdetermines a target AMF set according to Table 2, and selects one AMFfrom the AMF set as the initial AMF. For example, the base stationdetermines, based on the 5G GUTI of the UE, that the AMF region is X,the AMF set is A, and a region Y corresponding to the base station isnot in X. The base station determines, according to Table 2, that aproper AMF set is B, and selects one AMF from B as the initial AMFaccording to a preset policy.

Step 604: The AMF 1 receives the registration request sent by the 5Gbase station, and obtains a context of the UE from the MME.

Specifically, the AMF 1 may determine the MME based on the 5G GUTI, andsend a context request message to the determined MME. The MME sends thecontext of the UE to the AMF 1. The context of the UE includesinformation about an established PDN connection of the UE in the 4Gnetwork, and the information about the established PDN connection isspecifically information about a PGW-C/SMF or an APN corresponding tothe PDN connection.

Step 605: The AMF 1 obtains subscription data of the UE from a user datamanagement entity (HSS/UDM).

Step 605 is the same as step 305 in the foregoing embodiment. Forrelated content, refer to the foregoing descriptions. Details are notdescribed herein again.

Similar to the embodiment of FIG. 3 , the AMF 1 can determine, based onthe information about the PDN connection, a network slice correspondingto the PDN connection. Alternatively, the NSSF may determine, based onthe information about the PDN connection, a network slice correspondingto the PDN connection. In the following steps in this embodiment of thepresent disclosure, an example in which the NSSF determines, based onthe information about the PDN connection, the network slicecorresponding to the PDN connection is described.

Step 606: The AMF 1 sends a slice selection request to a network sliceselection function (NSSF).

The slice selection request includes the information about theestablished PDN connection, information about a subscribed network sliceof the UE, and the like.

Step 607: The NSSF receives the slice selection request sent by the AMF1, and returns a slice selection response to the AMF 1, where the sliceselection response includes information about a network slice allowedfor the UE (Allowed NSSAI) and information about a target AMF set.

Step 607 is the same as step 307 in the foregoing embodiment. Forrelated content, refer to the foregoing descriptions. Details are notdescribed herein again.

The AMF 1 receives the slice selection response returned by the NSSF.When the AMF 1 determines, based on the target AMF set, that the AMF 1can provide a service for the selected network slice, a subsequentregistration procedure (namely, step 610) is directly performed. Whenthe AMF 1 determines, based on the target AMF set, that the AMF 1 cannotprovide a service for the selected network slice, the following steps608 and 609 may be performed, that is, the AMF 1 selects one target AMFfrom the target AMF set for the UE, and sends the registration requestto the target AMF.

Step 608: The AMF 1 selects one AMF from the target AMF set as a targetAMF (an AMF 2).

Step 609: The AMF 1 forwards the registration request to the AMF 2,where the registration request includes the 5G GUTI of the UE and theinformation about the network slice allowed for the UE (Allowed NSSAI).

It should be noted that, for a PDN connection that cannot be handedover, the AMF 1 or the AMF 2 may return a handover reject message to theMME. Specifically, the AMF 1 or the AMF 2 may determine, based on thenetwork slice allowed for the UE and the network slice corresponding tothe established PDN connection, whether the network slice correspondingto the established PDN connection is included in the network sliceallowed for the UE. If the network slice corresponding to theestablished PDN connection is not included in the network slice allowedfor the UE, the AMF 1 or the AMF 2 determines that the PDN connectioncannot be handed over. After determining the PDN connection that cannotbe handed over, the AMF 1 or the AMF 2 returns the handover rejectmessage to the MME, where the handover reject message carriesinformation about the PDN connection that cannot be handed over, so thatthe MME subsequently initiates a corresponding PDN connection releaseprocedure.

In this embodiment of the present disclosure, if the UE registers withthe MME in the 4G network by using the 4G base station, and then is inan idle state, when moving to a coverage area of the 5G base station,the UE can be handed over to the 5G core network through a registrationprocedure. In this case, it is ensured that the UE can enjoy a networkservice equivalent to that in the 4G network.

FIG. 7 is a schematic flowchart of a mobility handover method. In thisembodiment, UE has currently registered with a 5G network by using anAMF, and the UE is in a connected state. When a source base stationfinds that the UE needs to be handed over, the source base stationselects a target base station. In this embodiment, the target basestation selected by the source base station is a base station connectedto a 4G network (E-UTRAN). The source base station sends a handoverrequest to the AMF, to initiate a handover procedure.

Step 701: The UE registers with the 5G network. In a process in whichthe UE registers with a 5GC, the AMF obtains 4G subscription data froman HSS/UDM, such as a usage type of the UE, and stores the 4Gsubscription data into a context of the UE.

Step 702: The source base station (NG-RAN) determines that the UE needsto be handed over to the target base station (E-UTRAN), and the sourcebase station sends a first handover request to the AMF, where the firsthandover request includes information about a target access region. TheAMF receives the first handover request sent by the source base station.

Step 702 is the same as step 301 in the foregoing embodiment. Forrelated content, refer to the foregoing embodiment. Details are notdescribed herein again.

Step 703: The AMF selects an MME.

Specifically, the AMF determines, based on the information about thetarget access region carried in the first handover request, that the UEneeds to be handed over to the 4G network. The AMF obtains acorresponding context of the UE based on an identifier of the userequipment, and determines, based on the UE usage type in the context,the MME that is to implement a handover operation. Alternatively, theAMF may obtain a corresponding context of the UE based on an identifierof the user equipment, and determine, based on a 5G GUTI in the contextof the UE and the information about the target access region, the MMEthat is to implement a handover operation. Alternatively, the AMF maydetermine a corresponding DCN identifier based on the 5G GUTI of the UE,and then determine, based on the DCN identifier and the informationabout the target access region, the MME that is to implement a handoveroperation.

The method for determining, by the AMF based on the UE usage type, theMME that is to implement a handover operation is the same as a process,during a 4G intra-network handover, in which the source MME determinesthe target MME based on the UE usage type. Details are not describedherein in this embodiment of the present disclosure.

The method for determining by the AMF based on the 5G GUTI of the UE andthe information about the target access region, the MME that is toimplement a handover operation is specifically as follows:

The AMF obtains, based on the 5G GUTI of the UE information about an AMFserving the UE (an AMF region and an AMF set), then queries thefollowing table based on a region (a target region) corresponding to thetarget access region, to determine a corresponding MME group, andselects one MME from the MME group as the MME that is to implement ahandover operation.

TABLE 3 AMF region AMF set Target region MME group X A Y B . . . . . . .. . . . .

That the AMF determines a corresponding DCN identifier based on the 5GGUTI of the UE, and then determines, based on the DCN identifier and theinformation about the target access region, the MME that is to implementa handover operation is specifically as follows:

The AMF obtains, based on the 5G GUTI of the UE, the information aboutthe AMF serving the UE (the information about the AMF region and theinformation about the AMF set), further queries the following table, todetermine the corresponding DCN identifier, and determines, based on theDCN identifier and the information about the target access region, theMME that is to implement a handover operation.

TABLE 4 Source AMF region AMF (optional) Set DCN X A B . . . . . . . . .

For the method for selecting an MME based on the DCN identifier and theinformation about the target access region, refer to an existingstandard.

According to the foregoing method for determining a target MME, the AMFmay determine the target MME by the AMF itself, or may determine thetarget MME by querying another device in the network, for example, aDNS. When the AMF determines the target MME by querying the DNS, theforegoing Table 3 and Table 4 are configured in the DNS, The AMF sendsrelated information to the DNS and the DNS returns a selected MME to theAMF.

Step 704: The AMF sends a second handover request to the target MME.

The second handover request includes the UE usage type and informationabout a PDN connection mapped from information about an established PDUsession of the UE in the 5G network.

Specifically, before the AMF sends the second handover request to thetarget MME, the method further includes: mapping, by the AMF, theinformation about the established PDU session of the UE in the 5Gnetwork to the information about the PDN connection. The informationabout the PDU session includes a data network name (DNN) andcorresponding S-NSSAI, and the information about the connection is anAPN.

That the AMF maps the information about the established PDU session ofthe UE in the 5G network to the information about the PDN connection isspecifically: mapping, by the AMF, the DNN in the information about thePDU session to a corresponding APN according to a preset first mappingrelationship; or mapping, by the AMF, the DNN and the S-NSSAI in theinformation about the PDU session to a corresponding APN according to apreset second mapping relationship.

The MME determines whether the UE usage type is supported, anddetermines, based on a subscribed APN and a configuration of the MME,whether the PDU session is allowed to be handed over to 4G DCN. For aPDU session that can be handed over, the MME requests the target basestation to allocate a resource, to perform a subsequent handoverprocedure. For a PDN connection that cannot be handed over, the MMEinstructs the AMF to reject a handover to the PDN connection, and theAMF instructs an SMF corresponding to the rejected PDN connection torelease a PDU session corresponding to the rejected PDN connection.

In this embodiment of the present disclosure, the AMF stores the 4Gsubscription data of the UE into the context of the UE in advance. Whendetermining that an inter-network handover of the UE from 5G to 4Goccurs, the AMF maps the information about the established PDU sessionin the 5G network to the information about the PDN connection, anddetermines a proper MME based on the 4G subscription data, to implementa fast inter-network handover. In addition, it is ensured that the UEcan enjoy an equivalent network service when moving from 5G to 4G.

FIG. 8 is a schematic flowchart of a mobility handover method. In thisembodiment, UE has registered with a 5G network by using an AMF, and theAMF has allocated allowed NSSAI to the UE. Then the UE enters an idlestate for a reason, and moves into a coverage area of a 4G base station.The UE registers with a 4G network by sending a location update request.When sending a context of the UE to an initial MME, the AMF sends 4Gsubscription data (including UE usage type) of the UE to the initialMME, and the initial MME selects a target MME based on the UE usagetype. Specifically, the method includes the following steps.

Step 801: The UE registers with the 5G network.

In a process in which the UE registers with a 5GC, the AMF obtains 4Gsubscription data from an HSS/UDM, such as a usage type of the UE, andstores the 4G subscription data into a context of the UE.

Step 802: The UE sends a location update request to the 4G base station,where the location update request includes a 4G GUTI mapped by the UEfrom a 5G GUTI. The 4G base station receives the location update requestsent by the UE.

Specifically, the UE determines, based on a tracking area identity list(TAI list) broadcast by the base station, that the UE moves out of anoriginal registration region, and that a new target cell selected by theUE is a cell covered by the 4G base station. Therefore, the UE sends thelocation update request to the 4G base station. The UE sends thelocation update request to the 4G base station by using an RRC messagebetween the UE and the 4G base station. If a DCN identifier isconfigured in the UE, the UE further adds the DCN identifier to the RRCmessage. The 4G base station selects an initial MME (an MME 1) for theUE based on the DCN identifier and location information of the UE. Thatthe UE maps the 5G GUTI to the 4G GUTI specifically includes: mapping anAMF region identifier and an AMF set identifier included in the 5G GUTIto an MME group identifier; or mapping an AMF region identifier and anAMF set identifier included in the 5G GUTI to an MME group identifierand an MME code number. Specifically, the AMF region identifier ismapped to the MME group identifier, and the AMF set identifier is mappedto the MME code number; or the AMF region identifier is mapped to a partof the MME group identifier, and the AMF set identifier is mapped to theother part of the MME group identifier.

Step 803: The 4G base station forwards the location update request to anMME 1.

Step 804: The MME 1 receives the location update request sent by the 4Gbase station, determines an AMF based on the 4G GUTI, and sends a UEcontext request message to the AMF.

Step 805: The AMF sends the context of the UE to the MME 1, where thecontext of the UE includes a UE usage type and information about a PDNconnection mapped from information about an established PINT session ofthe UE in the 5G network.

That the AMF maps information about an established PDU session of the UEin the 5G network to information about a PDN connection is specifically:mapping, by the AMF, the information about the established PDU sessionto the information about the PDN connection according to a configuredmapping relationship, where the information about the PDU sessionincludes a DNN and corresponding S-NSSAI, and the information about thePDN connection includes an APN. That the AMF maps information about anestablished PDU session of the UE in the 5G network to information abouta PDN connection is specifically: mapping, by the AMF, the DNN in theinformation about the PDU session to a corresponding APN according to apreset first mapping relationship; or mapping, by the AMF, the DNN andthe S-NSSAI in the information about the PDU session to a correspondingAPN according to a preset second mapping relationship.

Step 806: The MME 1 selects a DCN and a target MME (an MME 2) for theuser equipment based on the UE usage type.

In a possible case, the MME 1 determines, based on the UE usage type,that the target MME is the MME 1. In this case, a subsequent locationupdate procedure (step 810) is performed. Otherwise, steps 807 to 809are performed.

Step 807: The MME 1 sends a redirection request to the 4G base station,to request the 4G base station to send the location update request tothe MME 2.

Step 808: The 4G base station sends the location update request to theMME 2.

Step 809: The MME 2 determines an AMF based on the 4G GUTI in thelocation update request, and obtains the context of the UE from the AMF.

The context of the UE includes the UE usage type and the informationabout the PDN connection mapped from the information about theestablished PDU session of the UE in the 5G network.

The UE and the MME 2 perform a subsequent location update procedure.

In this embodiment of the present disclosure, the AMF stores the 4Gsubscription data of the UE into the context of the UE in advance. Whendetermining that an inter-network handover of the UE from 5G to 4Goccurs, the AMF maps the information about the established PDU sessionin the 5G network to the information about the PDN connection, anddetermines a proper MME based on the 4G subscription data, to implementa fast inter-network handover. In addition, it is ensured that the UEcan enjoy an equivalent network service when moving from 5G to 4G.

When a location of UE in a connected state changes, and the UE movesfrom an AMF (source AMF) region to another AMF (target AMF) region, thesource AMF obtains, based on information about an established PDUsession (such as S-NSSAI, optionally including an identifier of anetwork slice instance), the location of the UE, and information about asubscribed network slice of the UE, information about a network sliceallowed for the UE. As shown in FIG. 9 , a mobility management method isprovided, including the following steps.

Step 901: A source base station sends a first handover request to thesource AMF, where the first handover request includes information abouta target access region.

Specifically, the first handover request may be sent by the source basestation to the source AMF after a decision is made based on cellmeasurement information reported by the user equipment. The informationabout the target access region may include at least one of an identifierof a target cell, an identifier of a target base station, and anidentifier of a target tracking area. The identifier of the target cellis used to uniquely identify a target cell, and the target cell is acell to be accessed by the UE. The identifier of the target base stationis used to uniquely identify a target base station, and the target basestation is a base station to which the to-be-accessed cell belongs. Theidentifier of the target tracking area is used to uniquely identify atarget tracking area, and the target tracking area is a tracking area inwhich the to-be-accessed cell is located.

Step 902: The source AMF receives the first handover request sent by thesource base station, and determines a target AMF and information about anetwork slice allowed for the UE.

Specifically, the source AMF determines a target AMF in followingseveral methods.

In a possible implementation, as shown in Table 2 in the foregoingembodiment, a mapping relationship between information about the sourceAMF (information about a region in which the source AMF is located andinformation about a set to which the source AMF belongs), a targetregion, and a target AMF set is configured locally in the source AMF orin another device (for example, a network repository function NRFentity) in a network. Specifically, the source AMF queries the mappingrelationship based on the information about the AMF region in which thesource AMF is located, the information about the AMF set to which thesource AMF belongs, and the information about the target access region,to determine the target AMF set. Then the source AMF selects one AMFfrom the target AMF set as a target AMF according to a preset policy.

In another possible implementation, the source AMF sends a sliceselection request to an NSSF, and the slice selection request includesinformation about a network slice requested by the UE (Requested NSSAI),information about an established PDU session, and information about asubscribed network slice of the UE. The NSSF determines, based on theinformation about the network slice requested by the UE (RequestedNSSAI), the information about the established PDU session, and theinformation about the subscribed network slice of the UE, theinformation about the network slice allowed for the UE and informationabout the target AMF set. The information about the target AMF set maybe a list including an identifier of the target AMF set or an identifierof a candidate AMF. Optionally, the information about the establishedPDU session in the slice selection request may be replaced withinformation that is about a network slice corresponding to theestablished PDU session (corresponding S-NSSAI, optionally, furtherincluding an identifier of a network slice instance) and that isdetermined by the source AMF based on the information about theestablished PDU session. The information about the network slicerequested by the UE (Requested NSSAI) and the information about theestablished PDU session may be obtained from a context of the UE by thesource AMF based on an identifier of the UE. The information about theestablished PDU session may be an identifier of an SMF corresponding tothe PDU session.

Step 903: The source AMF sends a second handover request to the targetAMF, where the second handover request includes the information aboutthe network slice allowed for the UE. The target AMF receives the secondhandover request sent by the source AMF.

Optionally, the method further includes: determining, by the source AMFbased on the information about the established MU session and theinformation about the network slice allowed for the UE, a PDU sessionthat cannot be handed over, and sending, by the source AMF, a PDUsession release request message to an SMF corresponding to the PDUsession that cannot be handed over.

According to the method provided in this embodiment of the presentdisclosure, when the UE in a connected state moves from an AMF region toanother AMF region, a proper AMF may be selected to provide, for the UE,a service of accessing an al lowed network slice.

When UE registers with an AMF (a source AMF) in a 5G network, the sourceAMF allocates a 5G GUTI to the UE. Then the UE enters an idle state fora reason, and moves from an AMF (source AMF) region to another AMF(target AMF) region. In this case, the UE re-accesses the 5G networkthrough a registration procedure. As shown in FIG. 10 , a mobilitymanagement method is provided and includes the following steps.

Step 1001: The UE registers with the 5G network by using the source AMF.

When the UE registers with the 5G network by using the source AMF, thesource AMF allocates a 5G GUTI to the UE. The 5G GUTI includesinformation about the source AMF, for example, information about aregion in which the source AMF is located and information about a set towhich the source AMF belongs.

Step 1002: The UE initiates a registration request to a target basestation.

The registration request includes the 5G GUTI allocated by the sourceAMF to the UE. Optionally, the registration request further includesinformation (Requested NSSAI) about a network slice requested by the UE.

Step 1003: The target base station determines an initial AMF (an AMF 1in FIG. 10 ), and forwards the registration request to the AMF 1.

The target base station determines the initial AMF in a plurality ofmethods:

In a possible implementation, the target base station determines theinitial AMF based on the information about the network slice requestedby the UE carried in the registration request.

In another possible implementation, a default AMF is configured in thebase station. When receiving the registration request, the base stationuses the default AMF as the initial AMF.

In another possible implementation, the target base station queries aDNS based on the information about the region in which the source AMF islocated and the information about the AMF set to which the source AMFbelongs that are carried in the GUTI of the UE, and current regioninformation of the target base station (a location of the target basestation), to obtain the information about the target AMF set, where themapping relationship shown in Table 2 is configured in the DNS. Theinformation about the target AMF set may be an identifier of the targetAMF set or a list of identifiers of candidate target AMFs. Then thetarget base station selects one AMF from the target AMF set as theinitial AMF according to a preset policy.

Step 1004: The AMF 1 receives the registration request sent by thetarget base station, and obtains a context of the UE from the sourceAMF.

Specifically, the AMF 1 determines the source AMF based on the GUTI inthe registration request, and sends a UE context obtaining request tothe source AMR The context of the UE includes information about anestablished PDU session of the UE, and the information about theestablished PDU session includes an identifier of an SMF correspondingto the PDU session.

Step 1005: The AMF 1 obtains subscription data of the UE from a userdata management entity (HSS/UDM).

Step 1006: The AMF 1 sends a slice selection request to a network sliceselection function (NSSF).

Step 1007: The NSSF returns a slice selection response to the AMF 1,where the slice selection response includes information about a networkslice allowed for the UE (Allowed NSSAI) and information about a targetAMF set.

Step 1008: The AMF 1 selects one AMF from the target AMF set as a targetAMF (an AMF 2).

Step 1009: The AMF 1 forwards the registration request to the AMF 2,where the registration request includes the 5G GUTI of the UI; and theinformation about the network slice allowed for the UE (Allowed NSSAI).

Steps 1005 to step 1009 are the same as related steps in the foregoingembodiments. Details are not described herein again.

It should be noted that, for a PDU session that cannot be handed over,the AMF 1 or the AMF 2 may return a handover reject message to thesource AMF. Specifically, the AMF 1 or the AMF 2 may determine, based onthe network slice allowed for the UE and a network slice correspondingto the established PDU session, whether the network slice correspondingto the established PDU session is included in the network slice allowedfor the UE. If the network slice corresponding to the established PDUsession is not included in the network slice allowed for the UE, the AMF1 or the AMF 2 determines that the PDU session cannot be handed over.After determining the PDU session that cannot be handed over, the AMF 1or the AMF 2 returns the handover reject message to the source AMF,where the handover reject message carries information about the PDUsession that cannot be handed over, so that the source AMF subsequentlysends a PDU session release request message to an SMF corresponding tothe PDU session that cannot be handed over.

In this embodiment of the present disclosure, if the UE registers withthe source AMF in the 5G network by using the source base station, andthen is in an idle state, when moving from an AMF (source AMF) region toanother AMF (target AMF) region, the UE can re-register with the 5Gnetwork through a registration procedure. In this case, the UE canimplement a mobility handover.

The solutions in the embodiments of the present disclosure are mainlydescribed above from a perspective of interaction between networkelements. It can be understood that, to implement the foregoingfunctions, the mobility management entity (AMF or MME) and various basestations include a corresponding hardware structure and/or softwaremodule for performing the functions. A person skilled in the art shouldeasily be aware that, the present disclosure can be implemented in aform of hardware or in a form of a combination of hardware and computersoftware with reference to the example units and algorithm stepsdescribed in the embodiments disclosed in this specification. Whether afunction is performed by hardware or hardware driven by computersoftware depends on particular applications and design constraints ofthe technical solutions. A person skilled in the art may use differentmethods to implement the described functions for each particularapplication, but it should not be considered that the implementationgoes beyond the scope of the present disclosure.

In the embodiments of the present disclosure, division of functionmodules may be performed for the mobility management entity according tothe foregoing method examples. For example, the function modules may bedivided to correspond to the functions, or two or more functions may beintegrated into a processing module. The integrated module may beimplemented in a form of hardware, or may be implemented in a form of asoftware function module. It should be noted that the module division inthe embodiments of the present disclosure is an example, and is merelylogical function division and may be other division in actualimplementation. For example, if the function modules are divided tocorrespond to the functions, FIG. 11 is a possible schematic structuraldiagram of a mobility management apparatus in the foregoing embodiments.The apparatus 1100 includes: a first obtaining unit 1101 and a secondobtaining unit 1103. The first obtaining unit 1101 is configured toobtain information about an established PDN connection and informationabout a subscribed network slice of user equipment UE. The secondobtaining unit 1103 is configured to obtain, based on the informationabout the established PDN connection and the information about thesubscribed network slice, information about a network slice allowed forthe UE.

Optionally, that the second obtaining unit 1103 is configured to obtain,based on the information about the established PDN connection and theinformation about the subscribed network slice, information about anetwork slice allowed for the UE is specifically: determining, based onthe information about the established PDN connection, information abouta network slice corresponding to the established PDN connection; andobtaining, based on the information about the network slicecorresponding to the established PDN connection and the informationabout the subscribed network slice, the information about the networkslice allowed for the UE.

in a possible implementation, that the second obtaining unit 1103 isconfigured to obtain, based on the information about the established PDNconnection, information about a network slice corresponding to theestablished PDN connection is specifically: obtaining the informationabout the network slice corresponding to the established PDN connectionfrom a session management function entity corresponding to theestablished PDN connection.

In a possible implementation, that the second obtaining unit 1103 isconfigured to obtain, based on the information about the network slicecorresponding to the established PDN connection and the informationabout the subscribed network slice, the information about the networkslice allowed for the UE is specifically: sending a slice selectionrequest to a network slice selection function entity, where the sliceselection request includes the information about the network slicecorresponding to the established PDN connection and the informationabout the subscribed network slice; and receiving a slice selectionresponse returned by the network slice selection function entity, wherethe slice selection response includes the information about the networkslice allowed for the UE.

In a possible implementation, that the second obtaining unit 1103 isconfigured to obtain, based on the information about the established PDNconnection and the information about the subscribed network slice,information about a network slice allowed for the UE is specifically:sending a slice selection request to a network slice selection functionentity, where the slice selection request includes the information aboutthe established PDN connection and the information about the subscribednetwork slice; and receiving a slice selection response returned by thenetwork slice selection function entity, where the slice selectionresponse includes the information about the network slice allowed forthe UE.

The information about the established PDN connection is an identifier ofa session management function entity corresponding to the PDN connectionor an access point name APN corresponding to the PDN connection.

All related content of the steps in the foregoing method embodiments canbe used for function descriptions of the corresponding function modules.Details are not described herein again.

The foregoing mobility management apparatus can be implemented on anintegrated circuit (IC), a radio frequency integrated circuit (RFIC), aprinted circuit board (PCB), or the like. In addition, the apparatus canbe an independent device, or may be a part of a relatively large device.All related content of the steps in the foregoing method embodiments canbe used for function descriptions of the corresponding function modules.Details are not described herein again.

In this embodiment, the mobility management apparatus 1100 is presentedin a form of dividing the function modules to correspond to thefunctions, or the mobility management apparatus 1100 is presented in aform of dividing the function modules in an integrated manner. The“module” herein may be an application-specific integrated circuit(ASIC), a circuit, a processor and a memory for executing one or moresoftware or firmware programs, an integrated logic circuit, and/oranother device capable of providing the foregoing functions. In a simpleembodiment, a person skilled in the art may figure out that the mobilitymanagement apparatus 1100 may be implemented in a form shown in FIG. 2 .

For example, the processor 21 in FIG. 2 can invoke a computer executableinstruction stored in the memory 23, so that the mobility managementapparatus performs the mobility management method in the foregoingmethod embodiments. Specifically, the functions/an implementationprocess of the first obtaining unit 1101 and the second obtaining unit1103 in FIG. 11 can be implemented by the processor 21 in FIG. 2invoking the computer executable instruction stored in the memory 23.

As shown in FIG. 12 , a mobility management system 1200 is furtherprovided, and the system includes a network device 1201 and a firstmobility management entity 1203.

The network device 1201 is configured to: obtain a first mobilitymanagement entity based on a globally unique temporary identifier GUTIof user equipment UE or an identifier of a dedicated core networkaccessed by the UE, and information about a target access region of theUE, and send a first request message to the first mobility managemententity, where the includes information about a mobility managemententity serving the UE.

The first mobility management entity 1203 is configured to: obtaininformation about an established PDN connection and information about asubscribed network slice of the UE based on the received first requestmessage, and obtain, based on the information about the established PDNconnection and the information about the subscribed network slice,information about a network slice allowed for the UE.

In a possible implementation, the first request message is a handoverrequest or a registration request. When the first request message is ahandover request, the first request message includes the informationabout the established PDN connection. When the first request message isa registration request, the first request message includes the GUTI.That the first mobility management entity is configured to obtaininformation about an established PDN connection of the UE based on thereceived first request message is specifically: obtaining, by the firstmobility management entity based on the information that is about themobility management entity serving the UE and that is included in theGUTI, the information about the established PDN connection from themobility management entity serving the UE.

In a possible implementation, the information about the mobilitymanagement entity MME serving the UE is an identifier of the mobilitymanagement entity, where the identifier of the MME includes anidentifier of an MME group to which the MME belongs and an MME codenumber. That the network device obtains a first mobility managemententity based on a globally unique temporary identifier GUTI of userequipment UE and information about a target access region of the UE isspecifically: obtaining, by the network device, the first mobilitymanagement entity based on the identifier of the MME and the informationabout the target access region.

Optionally, the information about the mobility management entity servingthe UE is information about an access and mobility management functionAMF, where the information about the AMF includes information about aregion in which an AMF serving the UE is located and information about aset to which the AMF serving the UE belongs. That the network deviceobtains a first mobility management entity based on a globally uniquetemporary identifier GUTI of user equipment UE and information about atarget access region of the UE is specifically: obtaining, by thenetwork device, the first mobility management entity based on theinformation about the region in which the AMF serving the UE is located,the information about the set to which the AMF serving the UE islocated, and the information about the target access region.

It should be noted that, the first mobility management entity 1203 isthe same as the mobility management apparatus in FIG. 11 . All relatedcontent of the steps in the foregoing method embodiments can be used forfunction descriptions of the first mobility management entity 1203.Details are not described herein again.

Optionally, an embodiment of this application further provides a chipsystem, and the chip system includes a processor, configured to supporta mobility management apparatus in implementing the foregoing mobilitymanagement method. In a possible design, the chip system furtherincludes a memory. The memory is configured to store a programinstruction and data that are necessary for the mobility managementapparatus. The chip system may include a chip, or may include a chip andanother discrete device. This is not specifically limited in thisembodiment of this application.

Although the present disclosure is described with reference to theembodiments, in a process of implementing the present disclosure thatclaims protection, a person skilled in the art may understand andimplement another variation of the disclosed embodiments by viewing theaccompanying drawings, disclosed content, and the accompanying claims.In the claims, “comprising” does not exclude another component oranother step, and “a” or “one” does not exclude a meaning of plurality.A single processor or another unit may implement several functionsenumerated in the claims. Some measures are recorded in dependent claimsthat are different from each other, but this does not mean that thesemeasures cannot be combined to produce a better effect.

A person skilled in the art should understand that the embodiments ofthe present disclosure may be provided as a method, an apparatus(device), or a computer program product. Therefore, the presentdisclosure may use a form of hardware only embodiments, software onlyembodiments, or embodiments with a combination of software and hardware.Moreover, the present disclosure may use a form of a computer programproduct that is implemented on one or more computer-usable storage media(including but not limited to a disk memory, a CD-ROM, an opticalmemory, and the like) that include computer-usable program code. Thecomputer program is stored/distributed in a proper medium and isprovided as or used as a part of the hardware together with anotherhardware, or may also use another allocation form, such as by using theInternet or another wired or wireless telecommunications system.

The present disclosure is described with reference to the flowchartsand/or block diagrams of the method, the apparatus (device), and thecomputer program product according to the embodiments of the presentdisclosure. It should be understood that computer program instructionsmay be used to implement each process and/or each block in theflowcharts and/or the block diagrams and a combination of a processand/or a block in the flowcharts and/or the block diagrams. Thesecomputer program instructions may be provided for a general-purpose:computer, a dedicated computer, an embedded processor, or a processor ofany other programmable data processing device to generate a machine, sothat the instructions executed by a computer or a processor of any otherprogrammable data processing device generate an apparatus forimplementing a specific function in one or more procedures in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may also be stored in a computerreadable memory that can instruct the computer or any other programmabledata processing device to work in a specific manner, so that theinstructions stored in the computer readable memory generate an artifactthat includes an instruction apparatus. The instruction apparatusimplements a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions may also be loaded onto a computeror another programmable data processing device, so that a series ofoperations and steps are performed on the computer or the anotherprogrammable device, thereby generating computer-implemented processing.Therefore, the instructions executed on the computer or the anotherprogrammable device provide steps for implementing a specific functionin one or more procedures in the flowcharts and/or in one or more blocksin the block diagrams.

Although the present disclosure is described with reference to specificfeatures and the embodiments thereof, obviously, various modificationsand combinations may be made to them without departing from the spiritand scope of the present disclosure. Correspondingly, the specificationand accompanying drawings are merely examples of the present disclosuredefined by the accompanying claims, and is considered as any or all ofmodifications, variations, combinations or equivalents that cover thescope of the present disclosure. Obviously, a person skilled in the artcan make various modifications and variations to the present disclosurewithout departing from the spirit and scope of the present disclosure.The present disclosure is intended to cover these modifications andvariations provided that they fall within the scope of protectiondefined by the following claims and their equivalent technologies.

The invention claimed is:
 1. A mobility management method, wherein themethod comprises: obtaining, by a first mobility management entity, anidentifier of a session management function entity corresponding to anestablished Packet Data Network (PDN) connection of user equipment (UE);obtaining, by the first mobility management entity based on theidentifier of the session management function entity, information abouta network slice corresponding to the established PDN connection from thesession management function entity; and obtaining, by the first mobilitymanagement entity based on the information about the network slicecorresponding to the established PDN connection, information about anetwork slice allowed for the UE.
 2. The method according to claim 1,wherein the obtaining the information about the network slice allowedfor the UE comprises: sending, by the first mobility management entity,a slice selection request to a network slice selection function entity,wherein the slice selection request comprises the information about thenetwork slice corresponding to the established PDN connection; andreceiving, by the first mobility management entity, a slice selectionresponse from the network slice selection function entity, wherein theslice selection response comprises the information about the networkslice allowed for the UE.
 3. The method according to claim 2, whereinthe slice selection response further comprises a target access andmobility management function (AMF) set, and the method furthercomprises: determining, by the first mobility management entity based onthe target AMF set, a second mobility management entity; and sending, bythe first mobility management entity, a third request message to thesecond mobility management entity, wherein the third request messagecomprises the information about the network slice allowed for the UE. 4.The method according to claim 1, wherein the obtaining the identifier ofthe session management function entity corresponding to an establishedPDN connection comprises: receiving, by the first mobility managemententity, the identifier of the session management function entity from athird mobility management entity.
 5. The method according to claim 4,wherein the first mobility management entity is an access and mobilitymanagement function in a 5G network, and the third mobility managemententity is a mobility management entity in a 4G network.
 6. The methodaccording to claim 1, wherein the obtaining information about thenetwork slice corresponding to the established PDN connection comprises:sending, by the first mobility management entity based on the identifierof the session management function entity, a request message to thesession management function entity; receiving, by the first mobilitymanagement entity from the session management function entity, aresponse message including information about the network slicecorresponding to the established PDN connection.
 7. The method accordingto claim 1, wherein the identifier of the session management functionentity is a fully qualified domain name (FQDN) of the session managementfunction entity.
 8. An apparatus comprising: at least one processor; andat least one memory coupled to the at least one processor and storingprogram instructions for execution by the at least one processor andcausing the apparatus to: obtain an identifier of a session managementfunction entity corresponding to an established Packet Data Network(PDN) connection of user equipment (UE); obtain, based on the identifierof the session management function entity, information about a networkslice corresponding to the established PDN connection from the sessionmanagement function entity; and obtain, based on the information aboutthe network slice corresponding to the established PDN connection,information about a network slice allowed for the UE.
 9. The apparatusaccording to claim 8, wherein the program instructions further cause theapparatus to: send a slice selection request to a network sliceselection function entity, wherein the slice selection request comprisesthe information about the network slice corresponding to the establishedPDN connection; and receive a slice selection response from the networkslice selection function entity, wherein the slice selection responsecomprises the information about the network slice allowed for the UE.10. The apparatus according to claim 9, wherein the slice selectionresponse further comprises a target access and mobility managementfunction (AMF) set, and the program instructions further cause theapparatus to: determine, based on the target AMF set, a second mobilitymanagement entity; send a third request message to the second mobilitymanagement entity, wherein the third request message comprises theinformation about the network slice allowed for the UE.
 11. Theapparatus according to claim 8, wherein the program instructions furthercause the apparatus to: receive the identifier of the session managementfunction entity from a third mobility management entity.
 12. Theapparatus according to claim 11, wherein the apparatus is an access andmobility management function in a 5G network, and the third mobilitymanagement entity is a mobility management entity in a 4G network. 13.The apparatus according to claim 8, wherein the program instructionsfurther cause the apparatus to: send, based on the identifier of thesession management function entity, a request message to the sessionmanagement function entity; receive, from the session managementfunction entity, a response message including information about thenetwork slice corresponding to the established PDN connection.
 14. Theapparatus according to claim 8, wherein the identifier of the sessionmanagement function entity is a fully qualified domain name (FQDN) ofthe session management function entity.
 15. A mobility managementmethod, wherein the method comprises: obtaining, by a first mobilitymanagement entity, an identifier of a session management function entitycorresponding to an established Packet Data Network (PDN) connection ofuser equipment (UE); sending, by the first mobility management entitybased on the identifier of the session management function entity, arequest message for obtaining network slice corresponding to the PDNconnection to the session management function entity; receiving, by thesession management function entity, the request message from the firstmobility management entity; in response to the request message, sending,by the session management function entity, a response message to thefirst mobility management entity, wherein the response message comprisesinformation about the network slice corresponding to the established PDNconnection; receiving, by the first mobility management entity, theresponse message from the session management function entity; andobtaining, by the first mobility management entity based on theinformation about the network slice corresponding to the established PDNconnection, information about a network slice allowed for the UE. 16.The method according to claim 15, wherein the obtaining the informationabout the network slice allowed for the UE comprises: sending, by thefirst mobility management entity, a slice selection request to a networkslice selection function entity, wherein the slice selection requestcomprises the information about the network slice corresponding to theestablished PDN connection; and receiving, by the first mobilitymanagement entity, a slice selection response from the network sliceselection function entity, wherein the slice selection responsecomprises the information about the network slice allowed for the UE.17. The method according to claim 16, wherein the method furthercomprises: receiving, by the network slice selection function entity,the slice selection request from the first mobility management entity;determining, by the network slice selection function entity based on theinformation about the network slice corresponding to the established PDNconnection, information about the network slice allowed for the UE;sending, by the network slice selection function entity, the sliceselection response to the first mobility management entity.
 18. Themethod according to claim 17, the method further comprises: determining,by the network slice selection function entity, a target access andmobility management functions (AMF) set, and wherein the slice selectionresponse further comprises the target AMF set, determining, by the firstmobility management entity based on the target AMF set, a secondmobility management entity; and sending, by the first mobilitymanagement entity, a third request message to the second mobilitymanagement entity, wherein the third request message comprises theinformation about a network slice allowed for the UE.
 19. The methodaccording to claim 15, wherein the obtaining the identifier of thesession management function entity corresponding to an established PDNconnection comprises: receiving, by the first mobility managemententity, the identifier of the session management function entity from athird mobility management entity; wherein the first mobility managemententity is an access and mobility management function in a 5G network,and the third mobility management entity is a mobility management entityin a 4G network.
 20. The method according to claim 15, wherein theidentifier of the session management function entity is a fullyqualified domain name (FQDN) of the session management function entity.21. A mobility management system, wherein the system comprises: a firstmobility management entity configured to: obtain an identifier of asession management function entity corresponding to an establishedPacket Data Network (PDN) connection of user equipment (UE); send, basedon the identifier of the session management function entity, a firstrequest message to the session management function entity; receive afirst response message from the session management function entity,wherein the first response message comprises information about a networkslice corresponding to the established PDN connection; and obtain, basedon the information about the network slice corresponding to theestablished PDN connection, information about a network slice allowedfor the UE; and the session management function entity configured to:receive, from the first mobility management entity, the first requestmessage; and in response to the first request message, send the firstresponse message to the first mobility management entity.
 22. The systemaccording to claim 21, wherein: the system further comprises a networkslice selection function entity; the first mobility management entity isfurther configured to: send a slice selection request to the networkslice selection function entity; wherein the slice selection requestcomprises the information about the network slice corresponding to theestablished PDN connection; and receive a slice selection response fromthe network slice selection function entity, wherein the slice selectionresponse comprises the information about the network slice allowed forthe UE; and the network slice selection function entity is configuredto: receive the slice selection request from the first mobilitymanagement entity; determine, based on the information about the networkslice corresponding to the established PDN connection, information aboutthe network slice allowed for the UE; and send the slice selectionresponse to the first mobility management entity.
 23. The systemaccording to claim 22, wherein: the network slice selection functionentity is further configured to: determine, based on the informationabout the network slice corresponding to the established PDN connection,a target access and mobility management functions (AMF) set, and whereinthe slice selection response further comprises the target AMF set; thefirst mobility management entity is further configured to: determine,based on the target AMF set, a second mobility management entity; andsend a third request message to the second mobility management entity,wherein the third request message comprises the information about anetwork slice allowed for the UE.
 24. The system according to claim 21,wherein the first mobility management entity is further configured to:receive the identifier of the session management function entity from athird mobility management entity; wherein the first mobility managemententity is an access and mobility management function in a 5G network,and the third mobility management entity is a mobility management entityin a 4G network.
 25. The system according to claim 21, wherein theidentifier of the session management function entity is a fullyqualified domain name (FQDN) of the session management function entity.